Skip to content

[release-4.19] NO-JIRA: auditloganalyzer: update test name, remove duplicated test#29992

Closed
openshift-cherrypick-robot wants to merge 2 commits intoopenshift:release-4.19from
openshift-cherrypick-robot:cherry-pick-29930-to-release-4.19
Closed

[release-4.19] NO-JIRA: auditloganalyzer: update test name, remove duplicated test#29992
openshift-cherrypick-robot wants to merge 2 commits intoopenshift:release-4.19from
openshift-cherrypick-robot:cherry-pick-29930-to-release-4.19

Conversation

@openshift-cherrypick-robot
Copy link
Copy Markdown

@openshift-cherrypick-robot openshift-cherrypick-robot commented Jul 16, 2025

This is an automated cherry-pick of #29930

/assign vrutkovs

Vadim Rutkovsky added 2 commits July 16, 2025 06:48
auditloganalyzer: update test name to fail
239b7a5 
Ensure that we create a JUnit for an existing test - so it should have expected prefix and suffix
graceful_termination: remove duplicated test
b49fff6 
This test is already performed by auditloganalyzer
@openshift-cherrypick-robot openshift-cherrypick-robot mentioned this pull request Jul 16, 2025
Merged
@openshift-ci openshift-ci Bot requested review from celebdor and sjenning July 16, 2025 06:49
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Jul 16, 2025

@openshift-cherrypick-robot: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/okd-scos-e2e-aws-ovn b49fff6 link false /test okd-scos-e2e-aws-ovn
ci/prow/e2e-aws-ovn-kube-apiserver-rollout b49fff6 link false /test e2e-aws-ovn-kube-apiserver-rollout
ci/prow/e2e-aws-ovn-single-node-upgrade b49fff6 link false /test e2e-aws-ovn-single-node-upgrade

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@wangke19
Copy link
Copy Markdown
Contributor

wangke19 commented Jul 17, 2025

/lgtm

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Jul 17, 2025
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Jul 17, 2025

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: openshift-cherrypick-robot, wangke19
Once this PR has been reviewed and has the lgtm label, please assign neisw for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@wangke19
Copy link
Copy Markdown
Contributor

wangke19 commented Jul 17, 2025

/label qe-approved

@openshift-ci openshift-ci Bot added the qe-approved Signifies that QE has signed off on this PR label Jul 17, 2025
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jul 17, 2025
@openshift-ci-robot
Copy link
Copy Markdown

openshift-ci-robot commented Jul 17, 2025

@openshift-cherrypick-robot: This pull request explicitly references no jira issue.

Details

In response to this:

This is an automated cherry-pick of #29930

/assign vrutkovs

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@wangke19
Copy link
Copy Markdown
Contributor

wangke19 commented Jul 17, 2025

/jira refresh

@openshift-ci-robot
Copy link
Copy Markdown

openshift-ci-robot commented Jul 17, 2025

@wangke19: This pull request explicitly references no jira issue.

Details

In response to this:

/jira refresh

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-bot
Copy link
Copy Markdown
Contributor

openshift-bot commented Oct 16, 2025

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci openshift-ci Bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 16, 2025
@openshift-bot
Copy link
Copy Markdown
Contributor

openshift-bot commented Nov 15, 2025

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

@openshift-ci openshift-ci Bot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Nov 15, 2025
@openshift-bot
Copy link
Copy Markdown
Contributor

openshift-bot commented Dec 16, 2025

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

@openshift-ci openshift-ci Bot closed this Dec 16, 2025
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Dec 16, 2025

@openshift-bot: Closed this PR.

Details

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@celebdor celebdor Awaiting requested review from celebdor

@sjenning sjenning Awaiting requested review from sjenning

Assignees

@vrutkovs vrutkovs

@wangke19 wangke19

Labels

jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. qe-approved Signifies that QE has signed off on this PR

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

5 participants

@openshift-cherrypick-robot @wangke19 @openshift-ci-robot @openshift-bot @vrutkovs